Skip to content

Conversation

@fitzgen
Copy link
Member

@fitzgen fitzgen commented Jan 8, 2026

Builds on top of #12293

When doing plain old `cargo test -p wiggle` (or `wiggle-test`) the test would
fail due to linking errors because Wasmtime's `std` cargo feature (and maybe
others) wasn't being enabled. The crate's tests would pass when run as part of
the whole workspace, however, because of cargo feature resolution and other
crates that enabled the necessary features, which is why CI is green.
This is another interesting one because wasi-common is used internally to
Wasmtime but also by other projects. Therefore, rather than using
`wastime::error::*` and making `wasmtime` a hard dependency, we use just
`wasmtime_environ::error`.
@fitzgen fitzgen requested review from a team as code owners January 8, 2026 20:46
@fitzgen fitzgen requested review from dicej and removed request for a team January 8, 2026 20:46
@fitzgen fitzgen force-pushed the migrate-wasi-to-wasmtime-error branch 2 times, most recently from 680d7d4 to c89381f Compare January 8, 2026 21:07
@github-actions github-actions bot added the wasi Issues pertaining to WASI label Jan 8, 2026
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to rebase before merging to prune out the extra commits too? I don't think it'll matter in the end but it'll help clean up the merge commit message too

@fitzgen
Copy link
Member Author

fitzgen commented Jan 9, 2026

Might want to rebase before merging to prune out the extra commits too? I don't think it'll matter in the end but it'll help clean up the merge commit message too

I rebased a few PRs down the line, which cut a bunch of earlier commits out, don't really want to do O(n) rebases for such a deep stack, especially when I would have to wait for each PR to merge before rebasing the next. As you say, this just ends up including some old commit messages in the merge commit message, so not that big a deal IMO.

@fitzgen fitzgen added this pull request to the merge queue Jan 9, 2026
Merged via the queue into bytecodealliance:main with commit d73bd63 Jan 9, 2026
90 checks passed
@fitzgen fitzgen deleted the migrate-wasi-to-wasmtime-error branch January 9, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasi Issues pertaining to WASI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants